Point Cloud data (LAS format) from 2008 LiDAR, Andrews Experimental Forest

LAS file format

Thumbnail

Tags
topography, HJ Andrews Experimental Forest, Landscape Ecology, Oregon, geology, Blue River Watershed, LiDAR, digital elevation model (DEM), Willamette Basin


Summary

The purpose of the data is to provide users with a very accurate view of the topography of the study area. The data are suitable for creating visualizations, deriving watershed boundaries, creating stream networks, identifying structures such as roads and water features, looking at individual trees or stands of vegetation, and for identifying landslides and geological features,

Description

Watershed Sciences, Inc. (WS) collected Light Detection and Ranging (LiDAR) data from the H. J. Andrews and the Willamette National Forest (NF) on August 10th and 11th 2008. Total area for this AOI is 17,705 acres. The total area of delivered LiDAR including 100 m buffer is 19,493 acres. The point cloud data are available by request, as the files are too large to download over a network.

Credits

Data set was created by Watershed Sciences, Inc http://www.watershedsciences.com/

Use limitations

While substantial efforts are made to ensure the accuracy of data and documentation, complete accuracy of data sets cannot be guaranteed. All data are made available "as is". The Andrews LTER shall not be liable for damages resulting from any use or misinterpretation of data sets.

Extent

West -122.277460   East -122.099580
North 44.282961   South 44.19679

Scale Range
Maximum (zoomed in) 1:5,000
Minimum (zoomed out) 1:50,000

ArcGIS Metadata ▼►

Topics and Keywords  ▼►

Themes or categories of the resource  elevation


* Content type  Other Documents
Export to FGDC CSDGM XML format as Resource Description No

Place keywords  HJ Andrews Experimental Forest, Oregon, Blue River Watershed, Willamette Basin

Theme keywords  topography, Landscape Ecology, geology, LiDAR, digital elevation model (DEM)

Thesaurus  ▼►
Title Andrews Forest LTER Thesaurus


Hide Thesaurus ▲


Hide Topics and Keywords ▲

Citation  ▼►

Title Point Cloud data (LAS format) from 2008 LiDAR, Andrews Experimental Forest
Alternate titles  hja_be
Creation date 2008-11-14 00:00:00
Publication date 2012-11-21 00:00:00


Edition 1


Presentation formats  * digital document
FGDC geospatial presentation format  raster digital data


Other citation details gi01004


Hide Citation ▲

Citation Contacts  ▼►

Responsible party 
Organization's name Watershed Sciences
Individual's name Russell Faux
Contact's position Principle and Co-CEO
Contact's role  originator


Contact information  ▼►
Phone 
Voice 541-752-1204
Fax 541-752-3770

Address 
Type both
Delivery point 517 SW 2nd St. Suite 400
City Corvallis
Administrative area OR
Postal code 97333
Country US

Hide Contact information ▲


Responsible party 
Organization's name Forest Science Data Bank
Contact's role  publisher


Contact information  ▼►
Address 
Delivery point Corvallis, OR

Hide Contact information ▲


Responsible party 
Individual's name Theresa Valentine
Organization's name Corvallis Forest Science Laboratory
Contact's position Spatial Information Manger
Contact's role  point of contact


Contact information  ▼►
Phone 
Voice 541-750-7333
Fax 541-758-7760

Address 
Type both
Delivery point 3200 SW Jefferson Way
City Corvallis
Administrative area OR
Postal code 97332
Country US
e-mail address tvalentine@fs.fed.us or theresa.valentine@orst.edu

Hours of service m-f 8:00am-4:30pm
Hide Contact information ▲


Hide Citation Contacts ▲

Resource Details  ▼►

Dataset languages  English (UNITED STATES)
Dataset character set  utf8 - 8 bit UCS Transfer Format


Status  completed
Spatial representation type  grid


Spatial resolution 
Dataset's scale 
Scale denominator 1

Ground sample distance 
Precision of spatial data 1 m (meter)


* Processing environment Microsoft Windows 7 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.1.1.3143


Credits
Data set was created by Watershed Sciences, Inc  http://www.watershedsciences.com/
ArcGIS item properties 
* Name point_cloud.txt

Hide Resource Details ▲

Extents  ▼►

Extent 
Description
The LiDAR was flown on August 10th and 11, 2008 and processed data was delivered
                on November 14th, 2008.
Geographic extent 
Geographic description 
Geographic identifier 
Value testing one


Reference that defines the value  ▼►
Title Andrews LTER Site
Creation date 2013-03-15 00:00:00


Other citation details This is a test of what the geographic description should look like


Hide Reference that defines the value ▲


Description contains the resource No


Temporal extent 
Beginning date 2008-08-10 00:00:00
Ending date 2008-08-11 00:00:00

Extent 
Geographic extent 
Bounding rectangle 
Extent type  Extent used for searching
West longitude -122.277460
East longitude -122.099580
North latitude 44.282961
South latitude 44.19679
Extent contains the resource Yes

Hide Extents ▲

Resource Points of Contact  ▼►

Point of contact 
Individual's name Theresa Valentine
Organization's name Corvallis Forest Science Laboratory
Contact's position Spatial Information Manager
Contact's role  point of contact


Contact information  ▼►
Phone 
Voice 541-750-7333
Fax 541-750-7760

Address 
Type both
Delivery point 3200 SW Jefferson Way
City Corvallis
Administrative area Oregon
Postal code 97332
Country US
e-mail address tvalentine@fs.fed.us or theresa.valentine@orst.edu

Hours of service m-f 0800-1630
Hide Contact information ▲


Hide Resource Points of Contact ▲

Resource Maintenance  ▼►

Resource maintenance 
Update frequency  as needed


Hide Resource Maintenance ▲

Resource Constraints  ▼►

Constraints 
Limitations of use
While substantial efforts are made to ensure the accuracy of data and documentation, complete accuracy of data sets cannot be guaranteed. All data are made available "as is". The Andrews LTER shall not be liable for damages resulting from any use or misinterpretation of data sets.
Legal constraints 
Limitations of use
no legal constraints on use of this data. We ask that the following acknowledgements be made:
(see directions at this website  http://andrewsforest.oregonstate.edu/lter/acknowledgements.cf )
Access constraints  other restrictions
Use constraints  other restrictions


Other constraints
no legal constraints on use of this data. Please notify the Andrews staff of any data errors.
Hide Resource Constraints ▲

Spatial Reference  ▼►

Reference system identifier 
Value 26910


Hide Spatial Reference ▲

Spatial Data Properties  ▼►

Vector  ▼►
Level of topology for this dataset  topology 3D


Geometric objects 
Object type  point
Object count 966432159

Hide Vector ▲


Hide Spatial Data Properties ▲

Spatial Data Content  ▼►

Image Description 
Type of information  physical measurement
Attribute described by cell values elevation in meters


Band information 
Image quality code 
Value none


Processing level code 
Value none


Triangulation has been performed No
Radiometric calibration is available No
Camera calibration is available No
Film distortion information is available No
Lens distortion information is available No


Hide Spatial Data Content ▲

Data Quality  ▼►

Scope of quality information  ▼►
Resource level  dataset
Scope description 
Dataset HJA LiDAR flight of 2008

Hide Scope of quality information ▲


Data quality report - Absolute external positional accuracy  ▼►
Dimension vertical


Test date 2009-11-14 01:00:00


Measure name Manual System Calibration
Measure description The vertical accuracy of the LiDAR data is described as the mean and standard deviation (sigma ~ σ) of divergence of LiDAR point coordinates from RTK ground survey point coordinates. To provide a sense of the model predictive power of the dataset, the root mean square error (RMSE) for vertical accuracy is also provided. These statistics assume the error distributions for x, y, and z are normally distributed, thus we also consider the skew and kurtosis of distributions when evaluating error statistics. Statements of statistical accuracy apply to fixed terrestrial surfaces only and may not be applied to areas of dense vegetation or steep terrain. Additional control points are needed to assess accuracy in different land covers


Standard procedure identifier 
Value none


Quantitative test results 
Value 1
Units 
Symbol m

Evaluation type  direct internal
Evaluation method see above
Evaluation procedure  ▼►
Title LIDAR REMOTE SENSING DATA COLLECTION: HJ Andrews and Willamette NF
Publication date 2008-11-14 00:00:00


Edition 1
Edition date 2008-11-14


Resource location online 
Location http://andrewsforest.oregonstate.edu/lter/data/aerial/hj_andrews_report.pdf
Function performed  download

Hide Evaluation procedure ▲


Conformance test results 
Test passed Yes
Result explanation Project Average = 0.12 m o Median Relative Accuracy = 0.12 m o 1σ Relative Accuracy = 0.13 m o 2σ Relative Accuracy = 0.19 m


Product specification  ▼►
Title Accuracy
Creation date 2008-11-15 00:00:00


Presentation formats  digital document
FGDC geospatial presentation format  document


Resource location online 
Location http://andrewsforest.oregonstate.edu/lter/data/aerial/hj_andrews_report.pdf
Access protocol pdf file
Name LiDAR Remote Sensing Data Collection: HJ Andrews and Willamette NF, November 14, 2008
Description  chapeter on accuracy assessment
Function performed  download
Application profile pdf file

Hide Product specification ▲


Hide Data quality report - Absolute external positional accuracy ▲


Data quality report - Absolute external positional accuracy  ▼►
Dimension horizontal


Test date 2008-11-14 00:00:00


Measure description LiDAR survey datasets were referenced to the 1 Hz static ground GPS data collected over presurveyed monuments with known coordinates. While surveying, the aircraft collected 2 Hz kinematic GPS data, and the onboard inertial measurement unit (IMU) collected 200 Hz aircraft attitude data. Realm Survey Suite was used to process the kinematic corrections for the aircraft. The static and kinematic GPS data were then post-processed after the survey to obtain an accurate GPS solution and aircraft positions. POSPAC was used to develop a trajectory file that includes corrected aircraft position and attitude information. The trajectory data for the entire flight survey session were incorporated into a final smoothed best estimated trajectory (SBET) file that contains accurate and continuous aircraft positions and attitudes.


Standard procedure identifier 
Value LiDAR Remote Sensign Data Collection: HJ Andrews and Willamette NF November 14,2008


Reference that defines the value  ▼►
Title LiDAR Remote Sensign Data Collection: HJ Andrews and Willamette NF November 14,2008
Creation date 2008-11-14 00:00:00
Publication date 2008-11-14 00:00:00


Presentation formats  digital document
FGDC geospatial presentation format  document


Resource location online 
Location http://andrewsforest.oregonstate.edu/lter/data/aerial/hj_andrews_report.pdf
Access protocol pdf file
Function performed  download

Hide Reference that defines the value ▲


Quantitative test results 
Value 1
Units 
Symbol m

Evaluation type  direct internal
Evaluation method Manual System Calibration: Calibration procedures for each mission require solving geometric relationships that relate measured swath-to-swath deviations to misalignments of system attitude parameters. Corrected scale, pitch, roll and heading offsets were calculated and applied to resolve misalignments. The raw divergence between lines was computed after the manual calibration was completed and reported for each study area. 2. Automated Attitude Calibration: All data were tested and calibrated using TerraMatch automated sampling routines. Ground points were classified for each individual flight line and used for line-to-line testing. System misalignment offsets (pitch, roll and heading) and scale were solved for each individual mission and applied to respective mission datasets. The data from each mission were then blended when imported together to form the entire area of interest. 3. Automated Z Calibration: Ground points per line were utilized to calculate the vertical divergence between lines caused by vertical GPS drift. Automated Z calibration was the final step employed for relative accuracy calibration.
Evaluation procedure  ▼►
Title LiDAR Remote Sensign Data Collection: HJ Andrews and Willamette NF November 14,2008
Creation date 2008-11-14 00:00:00
Publication date 2008-11-14 00:00:00


Edition 1
Edition date 2008-11-14


Presentation formats  digital document
FGDC geospatial presentation format  document


Resource location online 
Location http://andrewsforest.oregonstate.edu/lter/data/aerial/hj_andrews_report.pdf
Access protocol pdf
Function performed  download

Hide Evaluation procedure ▲


Hide Data quality report - Absolute external positional accuracy ▲


Data quality report - Completeness omission  ▼►
Test date 2008-11-12 00:00:00


Measure description see description in on-line documentation


Standard procedure identifier 
Value none


Evaluation type  direct internal
Evaluation method see description in on-line documentation
Evaluation procedure  ▼►
Title LiDAR Remote Sensing Data Collection: HJ Andrews and Willamette NF
Creation date 2008-11-14 00:00:00
Publication date 2008-11-14 00:00:00


Edition 1
Edition date 2008-11-14


Resource location online 
Location http://andrewsforest.oregonstate.edu/lter/data/aerial/hj_andrews_report.pdf
Access protocol pdf
Function performed  download

Hide Evaluation procedure ▲


Hide Data quality report - Completeness omission ▲


Data quality report - Conceptual consistency  ▼►
Measure description see report from Watershed Sciences


Standard procedure identifier 
Value Document


Evaluation type  direct external
Evaluation method see documentation from Watershed Sciences
Evaluation procedure  ▼►
Title LiDAR Remote Senseing Data Collection: HJ Andrews and Willamette National Forests
Creation date 2008-11-14 00:00:00


Responsible party 
Organization's name Watershed Sciences
Contact's role  originator


Resource location online 
Location http://andrewsforest.oregonstate.edu/lter/data/aerial/hj_andrews_report.pdf
Function performed  download

Hide Evaluation procedure ▲


Hide Data quality report - Conceptual consistency ▲


Hide Data Quality ▲

Lineage  ▼►

Process step 
▼►
When the process occurred 2008-09-01 00:00:00
Description Simultaneous with the airborne data collection mission, we conducted multiple static (1 Hz recording frequency) ground surveys over monuments with known coordinates (Table 1). Indexed by time, these GPS data are used to correct the continuous onboard measurements of aircraft position recorded throughout the mission. Multiple sessions were processed over the same monument to confirm antenna height measurements and reported position accuracy. After the airborne survey, these static GPS data were then processed using triangulation with Continuously Operating Reference Stations (CORS) stations, and checked against the Online Positioning User Service (OPUS2) to quantify daily variance. Controls were located within 13 nautical miles of the mission area(s).


Hide Process step ▲


Process step 
▼►
When the process occurred 2008-10-01 00:00:00
Description Laser point coordinates were computed using the REALM software based on independent data from the LiDAR system (pulse time, scan angle), and aircraft trajectory data (SBET). Laser point returns (first through fourth) were assigned an associated (x, y, z) coordinate along with unique intensity values (0-255). The data were output into large LAS v. 1.1 files; each point maintains the corresponding scan angle, return number (echo), intensity, and x, y, z (easting, northing, and elevation) information. These initial laser point files were too large for subsequent processing. To facilitate laser point processing, bins (polygons) were created to divide the dataset into manageable sizes (< 500 MB). Flightlines and LiDAR data were then reviewed to ensure complete coverage of the study area and positional accuracy of the laser points. Laser point data were imported into processing bins in TerraScan, and manual calibration was performed to assess the system offsets for pitch, roll, heading and scale (mirror flex). Using a geometric relationship developed by Watershed Sciences, each of these offsets was resolved and corrected if necessary. LiDAR points were then filtered for noise, pits (artificial low points) and birds (true birds as well as erroneously high points) by screening for absolute elevation limits, isolated points and height above ground. Each bin was then manually inspected for remaining pits and birds and spurious points were removed. In a bin containing approximately 7.5-9.0 million points, an average of 50-100 points are typically found to be artificially low or high. Common sources of non-terrestrial returns are clouds, birds, vapor, haze, decks, brush piles, etc. Internal calibration was refined using TerraMatch. Points from overlapping lines were tested for internal consistency and final adjustments were made for system misalignments (i.e., pitch, roll, heading offsets and scale). Automated sensor attitude and scale corrections yielded 3-5 cm improvements in the relative accuracy. Once system misalignments were corrected, vertical GPS drift was then resolved and removed per flight line, yielding a slight improvement (<1 cm) in relative accuracy. The TerraScan software suite is designed specifically for classifying near-ground points (Soininen, 2004). The processing sequence began by ‘removing’ all points that were not ‘near’ the earth based on geometric constraints used to evaluate multi-return points. The resulting bare earth (ground) model was visually inspected and additional ground point modeling was performed in site-specific areas to improve ground detail. This manual editing of grounds often occurs in areas with known ground modeling deficiencies, such as: bedrock outcrops, cliffs, deeply incised stream banks, and dense vegetation. In some cases, automated ground point classification erroneously included known vegetation (i.e., understory, low/dense shrubs, etc.). These points were manually reclassified as non-grounds. Ground surface rasters were developed from triangulated irregular networks (TINs) of ground points.


Hide Process step ▲


Process step 
▼►
When the process occurred 2008-10-16 00:00:00
Description Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. Software: Waypoint GPS v.7.60 2. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with attitude data (sensor heading, position, and attitude are calculated throughout the survey). Software: IPAS v.1.4 3. Calculate laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Create raw laser point cloud data for the entire survey in *.las (ASPRS v1.1) format. Software: ALS Post Processing Software 4. Import raw laser points into subset bins (less than 500 MB, to accommodate file size constraints in processing software). Perform manual relative accuracy calibration and filter for pits/birds. Classify ground points for individual flight lines (to be used for relative accuracy testing and calibration). Software: TerraScan v.7.012 5. Test relative accuracy using ground classified points per each flight line. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Perform calibrations on ground classified points from paired flight lines. Every flight line is used for relative accuracy calibration. Software: TerraMatch v.7.004 6. Import position and attitude data. Classify ground and non-ground points. Assess statistical absolute accuracy via direct comparisons of ground classified points to ground RTK survey data. Convert data to orthometric elevations (NAVD88) by applying a Geoid03 correction. Create ground model as a triangulated surface and export as ArcInfo ASCII grids at the specified pixel resolution.


Hide Process step ▲


Process step 
▼►
When the process occurred 2008-10-16 00:00:00
Description The LiDAR survey uses a Leica ALS50 Phase II laser system. For the HJ Andrews and Willamette NF study areas, the sensor scan angle was ±14o from nadir1 with a pulse rate designed to yield an average native density (number of pulses emitted by the laser system) of 8 points per square meter over terrestrial surfaces. All study areas were surveyed with an opposing flight line side-lap of =50% (=100% overlap) to reduce laser shadowing and increase surface laser painting. The Leica ALS50 Phase II system allows up to four range measurements (returns) per pulse, and all discernable laser returns were processed for the output dataset. It is not uncommon for some types of surfaces (e.g. dense vegetation or water) to return fewer pulses than the laser originally emitted. These discrepancies between ‘native’ and ‘delivered’ density will vary depending on terrain, land cover and the prevalence of water bodies. To accurately solve for laser point position (geographic coordinates x, y, z), the positional coordinates of the airborne sensor and the attitude of the aircraft were recorded continuously throughout the LiDAR data collection mission. Aircraft position was measured twice per second (2 Hz) by an onboard differential GPS unit. Aircraft attitude was measured 200 times per second (200 Hz) as pitch, roll and yaw (heading) from an onboard inertial measurement unit (IMU). To allow for post-processing correction and calibration, aircraft/sensor position and attitude data are indexed by GPS time


Hide Process step ▲


Hide Lineage ▲

Distribution  ▼►

Distributor  ▼►
Contact information 
Individual's name Theresa Valentine
Organization's name Corvallis Forest Science Laboratory
Contact's position Spatial Information Manger
Contact's role  distributor


Contact information  ▼►
Phone 
Voice 541-750-7333
Fax 541-758-7760

Address 
Type both
Delivery point 3200 SW Jefferson Way
City Corvallis
Administrative area OR
Postal code 97332
Country US
e-mail address tvalentine@fs.fed.us or theresa.valentine@orst.edu

Hours of service m-f 8:00am-4:30pm
Hide Contact information ▲


Ordering process 
Instructions
Call contact person for instructions and costs.

Hide Distributor ▲


Distribution format 
Version unknown
Name LAS file format


Transfer options 
Units of distribution files on disk


Medium of distribution 
Medium name  hard disk


Limitations for using the medium need external hard drive for the 30 Gigabites of data. Total LiDAR data is over 40 GB.


Hide Distribution ▲

Fields  ▼►

Details for object Andrews LAS Files  ▼►
Type Point Record Data
Row count 966432159
Definition
Point Record Data format 0
Definition source
ASPRS LAS File specifications


Field x
  ▼►
Data type integer
Width 4
Field description
value of x  in meters
Description source
ASPRS LAS Format v 1.1
Description of values x coordinate value in meters


Hide Field x ▲


Field y
  ▼►
Data type integer
Width 4
Field description
Y value in meters
Description source
ASPRS LAS Format v 1.1
Description of values y coordinate value in meters


Accuracy information 
Accuracy y coordinate value in meters
Hide Field y ▲


Field Z
  ▼►
Data type integer
Width 4
Field description
Z coordinate (elevation) in meters
Description source
ASPRS LAS Format v 1.1
Description of values z value in meters (elevation)


Accuracy information 
Accuracy z value in meters (elevation)
Hide Field Z ▲


Field Intensity
  ▼►
Data type integer
Width 2
Field description
intensity of LiDAR pulse return magnitude
Description source
ASPRS LAS Format v 1.1
Description of values intensity of LiDAR pulse return magnitude


Accuracy information 
Accuracy intensity of LiDAR pulse return magnitude
Hide Field Intensity ▲


Field Return Number
  ▼►
Data type integer
Width 3
Field description
The return number is the pulse return number for a given output pulse. A
given output laser pulse can have many returns, and they must be marked in sequence of return.
The first return will have a return number of one, the second a return number of two, and so on
up to five returns.
Description source
ASPRS LAS Format v 1.1
Description of values The return number is the pulse return number for a given output pulse. A given output laser pulse can have many returns, and they must be marked in sequence of return. The first return will have a return number of one, the second a return number of two, and so on up to five returns.


Hide Field Return Number ▲


Field Number of Returns
  ▼►
Data type integer
Width 3
Field description
Number of Returns (for this emitted pulse): The number of returns is the total number of returns
for a given pulse. For example, a laser data point may be return two (return number) with a
total number of five returns.
Description source
ASPRS LAS Format v 1.1
Description of values Number of Returns (for this emitted pulse): The number of returns is the total number of returns for a given pulse. For example, a laser data point may be return two (return number) with a total number of five returns.


Accuracy information 
Accuracy number of returns for a given pulse
Hide Field Number of Returns ▲


Field Scan Direction Flag
  ▼►
Data type integer
Width 1
Field description
Scan Direction Flag: The scan direction flag denotes the direction at which the scanner mirror
was traveling at the time of the output pulse. A bit value of 1 is a positive scan direction, and a
bit value of 0 is a negative scan direction.
Description source
ASPRS LAS Format v 1.1
List of values 
Value 1
Description positive scan direction
Enumerated domain value definition source ASPRS LAS Format v 1.1


Value 0
Description negative scan direction
Enumerated domain value definition source ASPRS LAS Format v 1.1


Hide Field Scan Direction Flag ▲


Field Edge of Flight Line
  ▼►
Data type integer
Width 1
Field description
Edge of Flight Line: The edge of flight line data bit has a value of 1 only when the point is at the
end of a scan. It is the last point on a given scan line before it changes direction.
Description source
ASPRS LAS Format v 1.1
List of values 
Value 1
Description point is at the end of a scan
Enumerated domain value definition source ASPRS LAS Format v 1.1


Hide Field Edge of Flight Line ▲


Field classification
  ▼►
Data type integer
Width 1
Field description
Classification: Classification in LAS 1.0 was essentially user defined and optional. LAS 1.1
defines a standard set of ASPRS classifications. In addition, the field is now mandatory. If a
point has never been classified, this byte must be set to zero. There are no user defined classes
since both point format 0 and point format 1 supply 8 bits per point for user defined operations.
Description source
ASPRS LAS Format v 1.1
List of values 
Value 0
Description Created, never classified
Enumerated domain value definition source ASPRS LAS Format v 1.1


Value 1
Description unclassified
Enumerated domain value definition source ASPRS LAS Format v 1.1


Value 2
Description ground
Enumerated domain value definition source ASPRS LAS Format v 1.1


Value 3
Description low vegetation
Enumerated domain value definition source ASPRS LAS Format v 1.1


Value 4
Description medium vegetation
Enumerated domain value definition source ASPRS LAS Format v 1.1


Value 5
Description high vegetation
Enumerated domain value definition source ASPRS LAS Format v 1.1


Value 6
Description building
Enumerated domain value definition source ASPRS LAS Format v 1.1


Value 7
Description low point (noise)
Enumerated domain value definition source ASPRS LAS Format v 1.1


Value 8
Description model key-point (mass point)
Enumerated domain value definition source ASPRS LAS Format v 1.1


Value 9
Description water
Enumerated domain value definition source ASPRS LAS Format v 1.1


Value 10
Description reserved for ASPRS Definition
Enumerated domain value definition source ASPRS LAS Format v 1.1


Value 11
Description reserved for ASPRS Definition
Enumerated domain value definition source ASPRS LAS Format v 1.1


Value 12
Description overlap points
Enumerated domain value definition source ASPRS LAS Format v 1.1


Value 13-31
Description reserved for ASPRS Definition
Enumerated domain value definition source ASPRS LAS Format v 1.1


Hide Field classification ▲


Field Scan Angel Rank (-90 to +90) - left side
  ▼►
Data type characterString
Width 1
Field description
Scan Angle Rank: The scan angle rank is a signed one-byte number with a valid range from -90
to +90. The scan angle rank is the angle (rounded to the nearest integer in the absolute value
sense) at which the laser point was output from the laser system including the roll of the aircraft.
The scan angle is within 1 degree of accuracy from +90 to –90 degrees. The scan angle is an
angle based on 0 degrees being NADIR, and –90 degrees to the left side of the aircraft in the
direction of flight.
Description source
ASPRS LAS Format v 1.1
Description of values The scan angle rank is a signed one-byte number with a valid range from -90 to +90.


Hide Field Scan Angel Rank (-90 to +90) - left side ▲


Field user data
  ▼►
Data type characterstring
Width 1
Field description
User Data: This field may be used at the user’s discretion.
Description source
ASPRS LAS Format v 1.1
Description of values no information on the values in this field. contact Watershed Sciences for more information.


Hide Field user data ▲


Field Point Source ID
  ▼►
Data type integer
Width 2
Field description
Point Source ID: This value indicates the file from which this point originated. Valid values for
this field are 1 to 65,535 inclusive with zero being used for a special case discussed below. The
numerical value corresponds to the File Source ID from which this point originated. Zero is
reserved as a convenience to system implementers. A Point Source ID of zero implies that this
point originated in this file. This implies that processing software should set the Point Source ID
equal to the File Source ID of the file containing this point at some time during processing.
Description source
ASPRS LAS Format v 1.1
Description of values Point Source ID: This value indicates the file from which this point originated. Valid values for this field are 1 to 65,535 inclusive with zero being used for a special case discussed below. The numerical value corresponds to the File Source ID from which this point originated. Zero is reserved as a convenience to system implementers. A Point Source ID of zero implies that this point originated in this file. This implies that processing software should set the Point Source ID equal to the File Source ID of the file containing this point at some time during processing. We are using both 0 and 1 as Unclassified to maintain compatibility with current popular classification software such as TerraScan. We extend the idea of classification value 1 to include cases in which data have been subjected to a classification algorithm but emerged in an undefined state. For example, data with class 0 is sent through an algorithm to detect man-made structures – points that emerge without having been assigned as belonging to structures could be remapped from class 0 to class 1.


Hide Field Point Source ID ▲


Hide Details for object Andrews LAS Files ▲


Overview Description 
▼►
Entity and Attribute Overview The LAS files are developed according to the LAS Specifications. There are several attributes that are defined in the specification.


Entity and Attribute Detail Citation LAS Specification Version 1.` from the ASPRS standard. The Specification and attribute descriptions are available at http://asprs.org/a/society/committees/standards/asprs_las_format_v11.pdf


Hide Overview Description ▲


Hide Fields ▲

References  ▼►

Aggregate Information 
Association type  cross reference


Aggregate resource name  ▼►
Title LiDAR Remote Sensing Data Collection HJ Andrews and Willamette National Forest
Creation date 2008-11-14 00:00:00
Publication date 2012-11-14 00:00:00


Edition 1


Presentation formats  hardcopy document
FGDC geospatial presentation format  document


Responsible party 
Organization's name Watershed Sciences
Contact's role  originator


Hide Aggregate resource name ▲


Hide References ▲

Metadata Details  ▼►

* Metadata language English (UNITED STATES)
Metadata character set  utf8 - 8 bit UCS Transfer Format


Scope of the data described by the metadata  dataset
Scope name  * non-geographic dataset


* Last update 2013-06-14


ArcGIS metadata properties
Metadata format ArcGIS 1.0
Metadata style FGDC CSDGM Metadata
Standard or profile used to edit metadata FGDC


Created in ArcGIS for the item 2013-03-20 11:56:43
Last modified in ArcGIS for the item 2013-06-14 13:41:33


Automatic updates
Have been performed Yes
Last update 2013-06-14 13:41:33


Hide Metadata Details ▲

Metadata Contacts  ▼►

Metadata contact 
Individual's name Theresa Valentine
Organization's name Corvallis Forest Science Laboratory
Contact's position Spatial Information Manager
Contact's role  point of contact


Contact information  ▼►
Phone 
Voice 541-750-7333
Fax 541-758-7760

Address 
Type both
Delivery point 3200 SW Jefferson Way
City Corvallis
Administrative area Oregon
Postal code 97332
Country US
e-mail address tvalentine@fs.fed.us or theresa.valentine@orst.edu

Hours of service m-f 8:00am-4:00pm
Hide Contact information ▲


Hide Metadata Contacts ▲

Metadata Maintenance  ▼►

Maintenance 
Update frequency  as needed


Scope of the updates  feature


Hide Metadata Maintenance ▲

Metadata Constraints  ▼►

Security constraints 
Classification  unclassified


Hide Metadata Constraints ▲

FGDC Metadata (read-only) ▼►

Entities and Attributes  ▼►

Detailed Description
Entity Type
Entity Type Label Andrews LAS Files
Entity Type Definition
Point Record Data format 0
Entity Type Definition Source ASPRS LAS File specifications

Attribute
Attribute Label x
Attribute Definition
value of x in meters
Attribute Definition Source ASPRS LAS Format v 1.1
Attribute Domain Values
Unrepresentable Domain
x coordinate value in meters

Attribute
Attribute Label y
Attribute Definition
Y value in meters
Attribute Definition Source ASPRS LAS Format v 1.1
Attribute Domain Values
Unrepresentable Domain
y coordinate value in meters
Attribute Value Accuracy Information
Attribute Value Accuracy y coordinate value in meters

Attribute
Attribute Label Z
Attribute Definition
Z coordinate (elevation) in meters
Attribute Definition Source ASPRS LAS Format v 1.1
Attribute Domain Values
Unrepresentable Domain
z value in meters (elevation)
Attribute Value Accuracy Information
Attribute Value Accuracy z value in meters (elevation)

Attribute
Attribute Label Intensity
Attribute Definition
intensity of LiDAR pulse return magnitude
Attribute Definition Source ASPRS LAS Format v 1.1
Attribute Domain Values
Unrepresentable Domain
intensity of LiDAR pulse return magnitude
Attribute Value Accuracy Information
Attribute Value Accuracy intensity of LiDAR pulse return magnitude

Attribute
Attribute Label Return Number
Attribute Definition
The return number is the pulse return number for a given output pulse. A given output laser pulse can have many returns, and they must be marked in sequence of return. The first return will have a return number of one, the second a return number of two, and so on up to five returns.
Attribute Definition Source ASPRS LAS Format v 1.1
Attribute Domain Values
Unrepresentable Domain
The return number is the pulse return number for a given output pulse. A given output laser pulse can have many returns, and they must be marked in sequence of return. The first return will have a return number of one, the second a return number of two, and so on up to five returns.

Attribute
Attribute Label Number of Returns
Attribute Definition
Number of Returns (for this emitted pulse): The number of returns is the total number of returns for a given pulse. For example, a laser data point may be return two (return number) with a total number of five returns.
Attribute Definition Source ASPRS LAS Format v 1.1
Attribute Domain Values
Unrepresentable Domain
Number of Returns (for this emitted pulse): The number of returns is the total number of returns for a given pulse. For example, a laser data point may be return two (return number) with a total number of five returns.
Attribute Value Accuracy Information
Attribute Value Accuracy number of returns for a given pulse

Attribute
Attribute Label Scan Direction Flag
Attribute Definition
Scan Direction Flag: The scan direction flag denotes the direction at which the scanner mirror was traveling at the time of the output pulse. A bit value of 1 is a positive scan direction, and a bit value of 0 is a negative scan direction.
Attribute Definition Source ASPRS LAS Format v 1.1
Attribute Domain Values
Enumerated Domain
Enumerated Domain Value 1
Enumerated Domain Value Definition
positive scan direction
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1
Enumerated Domain
Enumerated Domain Value 0
Enumerated Domain Value Definition
negative scan direction
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1

Attribute
Attribute Label Edge of Flight Line
Attribute Definition
Edge of Flight Line: The edge of flight line data bit has a value of 1 only when the point is at the end of a scan. It is the last point on a given scan line before it changes direction.
Attribute Definition Source ASPRS LAS Format v 1.1
Attribute Domain Values
Enumerated Domain
Enumerated Domain Value 1
Enumerated Domain Value Definition
point is at the end of a scan
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1

Attribute
Attribute Label classification
Attribute Definition
Classification: Classification in LAS 1.0 was essentially user defined and optional. LAS 1.1 defines a standard set of ASPRS classifications. In addition, the field is now mandatory. If a point has never been classified, this byte must be set to zero. There are no user defined classes since both point format 0 and point format 1 supply 8 bits per point for user defined operations.
Attribute Definition Source ASPRS LAS Format v 1.1
Attribute Domain Values
Enumerated Domain
Enumerated Domain Value 0
Enumerated Domain Value Definition
Created, never classified
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1
Enumerated Domain
Enumerated Domain Value 1
Enumerated Domain Value Definition
unclassified
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1
Enumerated Domain
Enumerated Domain Value 2
Enumerated Domain Value Definition
ground
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1
Enumerated Domain
Enumerated Domain Value 3
Enumerated Domain Value Definition
low vegetation
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1
Enumerated Domain
Enumerated Domain Value 4
Enumerated Domain Value Definition
medium vegetation
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1
Enumerated Domain
Enumerated Domain Value 5
Enumerated Domain Value Definition
high vegetation
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1
Enumerated Domain
Enumerated Domain Value 6
Enumerated Domain Value Definition
building
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1
Enumerated Domain
Enumerated Domain Value 7
Enumerated Domain Value Definition
low point (noise)
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1
Enumerated Domain
Enumerated Domain Value 8
Enumerated Domain Value Definition
model key-point (mass point)
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1
Enumerated Domain
Enumerated Domain Value 9
Enumerated Domain Value Definition
water
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1
Enumerated Domain
Enumerated Domain Value 10
Enumerated Domain Value Definition
reserved for ASPRS Definition
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1
Enumerated Domain
Enumerated Domain Value 11
Enumerated Domain Value Definition
reserved for ASPRS Definition
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1
Enumerated Domain
Enumerated Domain Value 12
Enumerated Domain Value Definition
overlap points
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1
Enumerated Domain
Enumerated Domain Value 13-31
Enumerated Domain Value Definition
reserved for ASPRS Definition
Enumerated Domain Value Definition Source
ASPRS LAS Format v 1.1

Attribute
Attribute Label Scan Angel Rank (-90 to +90) - left side
Attribute Definition
Scan Angle Rank: The scan angle rank is a signed one-byte number with a valid range from -90 to +90. The scan angle rank is the angle (rounded to the nearest integer in the absolute value sense) at which the laser point was output from the laser system including the roll of the aircraft. The scan angle is within 1 degree of accuracy from +90 to –90 degrees. The scan angle is an angle based on 0 degrees being NADIR, and –90 degrees to the left side of the aircraft in the direction of flight.
Attribute Definition Source ASPRS LAS Format v 1.1
Attribute Domain Values
Unrepresentable Domain
The scan angle rank is a signed one-byte number with a valid range from -90 to +90.

Attribute
Attribute Label user data
Attribute Definition
User Data: This field may be used at the user’s discretion.
Attribute Definition Source ASPRS LAS Format v 1.1
Attribute Domain Values
Unrepresentable Domain
no information on the values in this field. contact Watershed Sciences for more information.

Attribute
Attribute Label Point Source ID
Attribute Definition
Point Source ID: This value indicates the file from which this point originated. Valid values for this field are 1 to 65,535 inclusive with zero being used for a special case discussed below. The numerical value corresponds to the File Source ID from which this point originated. Zero is reserved as a convenience to system implementers. A Point Source ID of zero implies that this point originated in this file. This implies that processing software should set the Point Source ID equal to the File Source ID of the file containing this point at some time during processing.
Attribute Definition Source ASPRS LAS Format v 1.1
Attribute Domain Values
Unrepresentable Domain
Point Source ID: This value indicates the file from which this point originated. Valid values for this field are 1 to 65,535 inclusive with zero being used for a special case discussed below. The numerical value corresponds to the File Source ID from which this point originated. Zero is reserved as a convenience to system implementers. A Point Source ID of zero implies that this point originated in this file. This implies that processing software should set the Point Source ID equal to the File Source ID of the file containing this point at some time during processing. We are using both 0 and 1 as Unclassified to maintain compatibility with current popular classification software such as TerraScan. We extend the idea of classification value 1 to include cases in which data have been subjected to a classification algorithm but emerged in an undefined state. For example, data with class 0 is sent through an algorithm to detect man-made structures – points that emerge without having been assigned as belonging to structures could be remapped from class 0 to class 1.

Overview Description
Entity and Attribute Overview
The LAS files are developed according to the LAS Specifications.  There are several attributes that are defined in the specification.
Entity and Attribute Detail Citation
LAS Specification Version 1.`  from the ASPRS standard.
The Specification and attribute descriptions are available at http://asprs.org/a/society/committees/standards/asprs_las_format_v11.pdf

Hide Entities and Attributes ▲